System and method for providing comprehensive vehicle build information

ABSTRACT

A hosted web-accessible system, computer program and methods are provided for generating comprehensive vehicle trim and detailed equipment information for clients, including providing comparative estimation based on underlying information regarding a particular vehicle. Comprehensive original vehicle data is obtained from vehicle manufacturers via a vehicle source interface, the data including a unique vehicle identifier for each of one or more vehicles associated with the respective source. A vehicle information request with a vehicle identifier is received from a client, and comprehensive original vehicle data is identified based on the unique identifier and the identifier from the client request. A client response interface displays vehicle data from the identified set of comprehensive original vehicle data. Vehicle valuation may be obtained from third party evaluators according to the vehicle request and based on the original vehicle data.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/188,604 filed Mar. 1, 2021 and titled “Web-based System and Method for Providing Comprehensive Vehicle Build Information”, which is a continuation of U.S. patent application Ser. No. 16/114,931 filed Aug. 28, 2018 and titled “Web-based System and Method for Providing Comprehensive Vehicle Build Information”, which is a continuation-in-part of U.S. patent application Ser. No. 13/297,438, filed on Nov. 16, 2011 and titled “Web-based System and Method for Providing Comprehensive Vehicle Build Information,” which claimed benefit of and priority from: U.S. Provisional Patent Application No. 61/415,207, filed on Nov. 18, 2010, each of which is hereby incorporated by reference in its entirety.

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the reproduction of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

The present disclosure relates generally to web-based systems and methods for providing and verifying vehicle information which is otherwise difficult to access or even unavailable, including providing comparative estimation based on underlying information regarding a particular vehicle. More particularly, the present disclosure relates to a host system and associated methods for producing and generating detailed information about the trim and optional equipment of a vehicle based on data provided from the vehicle manufacturer and a vehicle identifier provided from a third party entity such as a lender, dealer, auction or other consumer.

Currently, a vehicle has a vehicle identification number (VIN) that may provide basic information about the vehicle that has been coded into the VIN by a corresponding manufacturer. The information provided may include for example the country of origin, manufacturer, year of manufacture, manufacturing assembly plant, make and model, etc., but often is silent regarding the trim details and any upgrades related to the vehicle. This leaves the dealer, bank, customer, auction, and other entities having to visually verify items such as trim levels, transmission, optional packages, and/or other equipment for the vehicle, which may be quite difficult or even impossible to do in some cases where the vehicle is in another location and/or without knowing exactly what to look for and being willing to spend the time to look in the appropriate places. Often manufacturers have packages such as “sport” or “convenience” and trim levels such as “touring” or “grand touring” that can equate to hundreds or thousands of dollars in added value. Often they are not designated on the vehicle and are not coded in the VIN, leaving only a select number of individuals with detailed factory knowledge able to accurately identify or verify these vehicles, resulting often in misrepresentation or errors in determining value. Such errors and/or misrepresentations can lead to added exposure, risk, liability, and lost revenue to parties involved such as lenders, dealers and auctions.

As loan approvals, loan terms, pricing and buying decisions are determined from a value of the vehicle which relies to some extent on this information, it is crucial to accurately determine a vehicle's build information, trim details and optional equipment.

BRIEF SUMMARY OF THE INVENTION

A hosted web-accessible system, computer program and methods are provided in accordance with various embodiments of the present disclosure for accurately generating vehicle build information such as trim and detailed equipment information for clients, which is comprehensive in that it includes information which is both coded and non-coded in the VIN and further both verifiable and non-verifiable via mere visual inspection of the vehicle. Comprehensive original vehicle data is obtained from vehicle manufacturers via a vehicle source interface, the data including a unique vehicle identifier for each of one or more vehicles associated with the respective source. A vehicle information request with a vehicle identifier is received from a client via a client request interface, and comprehensive original vehicle data is identified based on the unique identifier from the source and the identifier from the client request. A client response interface is generated for the purpose of, among other things, displaying the identified set of comprehensive original vehicle data.

In certain embodiments of the disclosure, a vehicle valuation is obtained from third party evaluators according to the vehicle request and based on the original vehicle data.

In further embodiments, supplemental data may be received from service providers and optionally presented as well.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram representing an embodiment of a hosted system in accordance with the present disclosure.

FIG. 2 is a flowchart representing an embodiment of a method in accordance with the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

Referring generally to FIGS. 1 and 2 , various embodiments are described herein for a system, program product, and associated methods for providing comprehensive vehicle build data, trim and other detailed vehicle information such as optional equipment. Clients of a hosted system according to the present disclosure may obtain or otherwise view a report of verified vehicle information having been originally provided from the vehicle manufacturer, and in certain embodiments may further obtain a valuation for the vehicle as generated by a third party vehicle evaluator, and/or supplemental data from third party service providers having access to vehicle data downstream from the associated manufacturers.

Where the various figures may describe embodiments sharing various common elements and features with other embodiments, similar elements and features are given the same reference numerals and redundant description thereof may be omitted below. Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context dictates otherwise. The meanings identified below do not necessarily limit the terms, but merely provide illustrative examples for the terms. The meaning of “a,” “an,” and “the” may include plural references, and the meaning of “in” may include “in” and “on.” The phrase “in one embodiment,” as used herein does not necessarily refer to the same embodiment, although it may.

Terms such as “providing,” “processing,” “supplying,” “determining,” “calculating” or the like may refer at least to an action of a computer system, computer program, signal processor, logic or alternative analog or digital electronic device that may be transformative of signals represented as physical quantities, whether automatically or manually initiated.

Referring first to FIG. 1 , an embodiment of a web-based system 10 according to the present disclosure may be described. The term “web-based system” as used herein may, unless otherwise stated, refer generally to a platform effective to implement web-transitory functions, whether browser-based or otherwise. In other embodiments, the host system may include other computer-based platforms such as for example peer-to-peer structures which may not be explicitly web-based.

The system 10 is embodied by or within either of a central hosted server 12 or a plurality of servers 12 functionally linked and collectively defining a distributed host network (not shown). The server 12 as represented in FIG. 1 further includes a processor 14, a computer-readable memory medium 16, a database 20 and an I/O platform 22 which may typically include one or more user interfaces generated by program instructions or modules thereof in accordance with features, methods or steps described in greater detail below.

The term “computer-readable memory medium” as used herein may refer to any non-transitory medium 16 alone or as one of a plurality of non-transitory memory media 16 within which is embodied a computer program product 18 that includes processor-executable software, instructions or program modules which upon execution may provide data or otherwise cause a computer system to implement subject matter or otherwise operate in a specific manner as further defined herein. It may further be understood that more than one type of memory media may be used in combination to conduct processor-executable software, instructions or program modules from a first memory medium upon which the software, instructions or program modules initially reside to a processor for execution.

“Memory media” as generally used herein may further include without limitation transmission media and/or storage media. “Storage media” may refer in an equivalent manner to volatile and non-volatile, removable and non-removable media, including at least dynamic memory, application specific integrated circuits (ASIC), chip memory devices, optical or magnetic disk memory devices, flash memory devices, or any other medium which may be used to stored data in a processor-accessible manner, and may unless otherwise stated either reside on a single computing platform or be distributed across a plurality of such platforms. “Transmission media” may include any tangible media effective to permit processor-executable software, instructions or program modules residing on the media to be read and executed by a processor, including without limitation wire, cable, fiber-optic and wireless media such as is known in the art.

The term “processor” as used herein may refer to at least general-purpose or specific-purpose processing devices and/or logic as may be understood by one of skill in the art, including but not limited to single- or multithreading processors, central processors, parent processors, graphical processors, media processors, and the like.

The host server 12 may be accessible by or otherwise linked to various external and third party platforms via a communications network 34 and in accordance with these links is effective to collect, obtain, receive, transmit and/or share data using various communications protocols as are well known in the art. The term “communications network” 34 as used herein with respect to data communication between two or more parties or otherwise between communications network interfaces associated with two or more parties may refer to any one of, or a combination of any two or more of, telecommunications networks (whether wired, wireless, cellular or the like), a global network such as the Internet, local networks, network links, Internet Service Providers (ISP's), and intermediate communication interfaces as are known in the art.

The term “platform” as used herein may typically refer to a website, network, or alternative but equivalent interfaces for supporting multimedia interactivity consistent with the described features of the present disclosure

The I/O platform 22 represented in FIG. 1 may typically refer to one or more websites including a plurality of web pages, pop-ups, links and the like, or alternatively email, text, or equivalent messaging platforms, which collectively define the plurality of user interfaces further described herein. Such interfaces as may be associated with or generated by the host system in accordance with the present disclosure may include without limitation a client request interface 24, a client response interface 26, a vehicle source interface 28, a third party evaluator interface 30, and a vehicle service provider interface 32. It may be understood that the distinct interfaces as represented in FIG. 1 may be defined by or within a single website or even webpage having overlapping functionality, but this is by no means necessary within the scope of the present disclosure, and for example a “service provider” in one aspect may be a “vehicle source” or “client” in another aspect having access to the associated interfaces of the system.

A “client” as referred to herein may refer to any entity obtaining or seeking to obtain vehicle information utilizing the system and associated features of the present disclosure, including without limitation lenders, dealers, auction offices, auto evaluators, insurance agencies, automobile websites, law enforcement agencies or officers, individual consumers, etc.

A “vehicle source” may typically refer to a vehicle manufacturer but may further refer to any entity providing verifiable and comprehensive original vehicle data in accordance with the present disclosure.

“Comprehensive original vehicle data” as used throughout this description includes all vehicle data which is made available by the source and is relevant to the vehicle build data, trim, any optional detail information, vehicle valuation, etc., and generally includes information which is both coded and non-coded with respect to the vehicle identifier, and verifiable or non-verifiable by a user. Examples of such vehicle data may include standard information such as without limitation year, make and model of the vehicle. Other examples include factory information such as without limitation equipment, trim details, color, transmission details, drive train, factory packages, and factory options. Other examples include drivetrain information such as without limitation whether the vehicle is a four-wheel drive (4WD), a two-wheel drive (2WD, automatic 4WD, or all-wheel Drive (AWD). A “vehicle service provider” may typically refer to any party that provides supplemental vehicle data such as current aftermarket replacements, upgrades, and the like with respect to a vehicle. A service provider may be the manufacturer itself, or more typically may be a third party. Such third parties may in various embodiments of the present disclosure be able to provide supplemental vehicle data, but this data may typically be separated from the original data and identified as being less reliable than data from the vehicle source, and even made optional for viewing by clients of the system, as further described below.

A vehicle manufacturer may associate a Vehicle Identification Number (VIN) as a unique identifier of a particular manufactured vehicle. The VIN may be coded by the manufacturer according to one or more vehicle attributes, as known in the art. For example, information such as vehicle manufacturer country, region, or world manufacturer identifier may be included. The vehicle's make, mole, engine, weight, year, manufacturing plant, or vehicle description (e.g., to identify attributes such as model, body style, engine, etc.) may be included. One or more digits may provide a vehicle identification section relating to plant and other values, such as production number. The manufacturer generates a unique VIN for a particular car based on the combination of vehicle attributes and a possible sequence number.

However, it is not possible for a vehicle manufacturer to code all vehicle attributes in the VIN. As such, to sufficiently describe or value a particular vehicle, additional information must be known. In one exemplary embodiment, a vehicle manufacturer creates non-coded vehicle information relating to one or more attributes not coded in a VIN. The non-coded vehicle information is associated with a unique vehicle in one exemplary embodiment. Additionally or alternatively, at least a portion of non-coded vehicle information may relate to a plurality of vehicles sharing a common attribute, such as in the case of a non-VIN code trim package. The vehicle manufacturer may store or cause to be stored the non-coded vehicle information, and/or may convey the non-coded vehicle information to one or more external receivers, either together with the coded vehicle information, or separate from the coded vehicle information. In one exemplary embodiment, the coded and non-coded vehicle information is generated by the vehicle manufacturer at or around the time of vehicle manufacture.

Referring now to FIG. 2 , an exemplary method 100 in accordance with the present disclosure may be described. It may be understood that the various steps recited herein are not limiting on the scope of the present disclosure unless otherwise stated, and that accordingly the steps are not required to be executed in the order provided or even at all unless otherwise stated or where logic dictates.

In step 102, a host server receives, collects, imports, or otherwise obtains comprehensive original vehicle data directly from a vehicle source (typically the respective manufacturer) to ensure the accuracy of the associated information. The data may be obtained periodically from the source, for example at predetermined intervals, or simply as determined by the source such as where new data has become available. Generally speaking, the vehicle data may be transmitted via the communications network to a dedicated interface (e.g., secured web page, email address, etc.) in the form of an electronic data file, but alternatively may be simply made available for collection from a database residing on a source platform by program modules operating from the host server or otherwise executed by the host system on or within the source platform.

Typically, the comprehensive original vehicle data will include or be provided in association with a unique vehicle identifier, such as for example a VIN.

The data may upon importation or collection by the host system then be stored in a database (step 104). In various embodiments, the original data may be raw data from the source which is converted by the host system into a universal format for storage in a collective database. The raw data may be obtained using a predetermined format which merely requires the host system to parse, collate, arrange, etc., the data in order to properly store it within the database. Alternatively, the host system may require the use of algorithms or equivalent programmed functions to identify or characterize the raw data prior to storage. In some embodiments, each source/manufacturer may send raw data in a unique format which is configured to facilitate population of an intended client interface that is particular to the source, such as for example including source-specific trademarks, etc.

In certain embodiments of a host system within the scope of the present disclosure, vehicle service providers such as for example authorized dealers and the like may be allowed to provide supplemental (aftermarket) data to the system via a service provider interface. Where for example a service provider has modified, upgraded or removed some component as originally provided with respect to a particular vehicle, supplemental data may be provided to the system along with the unique vehicle identifier and then stored in the database alongside the comprehensive original vehicle data. The supplemental data will typically be stored in auxiliary portions of the database and not for example over or in place of the original data.

The supplemental data may further be stored in association with a service provider identifier. The particular service provider may in an embodiment be associated by the host system with a reliability score or the equivalent, so as to indicate the likelihood that the information is correct and complete based on prior dealings and/or client comments/feedback, or as a potential reflection on the quality of the vehicle itself after having received aftermarket servicing from that particular service provider, again based on prior dealings and/or client feedback. Algorithms for scoring the service providers, or interfaces for client feedback and association thereof with the particular service providers, may be executed by the host system automatically upon receipt of supplemental data or via a trigger where for example the service provider has previously received negative feedback or otherwise scored below a threshold value.

The client-specific portion of the process or in other words that related to a specific transaction or client request begins with step 106, wherein the host system receives a vehicle information request from a client via a dedicated interface (e.g., web page, pop-up data field, email address, etc.). The request typically shall include a vehicle identifier associated with the vehicle for which information is sought, and vehicle data corresponding with the particular vehicle may thereby be identified and retrieved from the database by matching the client-provided identifier with the unique identifier stored in association with the data. The vehicle identifier may be electronically scanned at the client end and submitted to the system interface, or alternatively manually entered via keystrokes and the like, equally within the scope of the present disclosure. Where the identifier is to be electronically scanned, the client-side hardware and associated software module necessary to generate the electronic identifier from (for example) the physical bar code is not itself generally associated with the host system of the present disclosure and further description is omitted herein as redundant.

In certain embodiments within the scope of the present disclosure, the system may generate a client response interface within or upon which is displayed at least a subset of the comprehensive original vehicle data for the identified vehicle (that which is associated with the vehicle identifier provided by the client), but not valuations or supplemental data. Such an embodiment may be optimal for an auction house, automobile website, or an equivalent client entity having no need of third party evaluations of the vehicle's value, or no desire to obtain potentially unreliable supplemental data from third party service providers. However, in other embodiments as are contemplated by a method 100 as represented in FIG. 2 , such features may be at least optionally provided by the system, as further described below.

Where a client has requested a vehicle valuation from the system (i.e., “yes” in response to the query in step 108), it may further be determined whether a third party book evaluator is available to provide valuation with respect to the identified vehicle (step 110). In some embodiments, this step may be redundant where the system is configured to provide all valuations internally and without the option of obtaining such valuations from an external source. In either event, where no evaluator is available or otherwise provided by the system for client selection (i.e., “no” in response to the query in step 110), the method 100 continues to step 112 and generates a vehicle valuation based on the comprehensive original vehicle data stored in the database. Program instructions or program modules which may be executed by the system to determine the value may include proprietary algorithms with respect to the host but are not so limited within the scope of the present disclosure.

In some embodiments, the system may generate or determine a first vehicle valuation based on the original data and further determine a second vehicle valuation which is based on the original data and any available supplemental data, such that either may be displayed for the client based on client selection.

Where one or more evaluators are available and provided by the system (in for example a list) for client selection (i.e., “yes” in response to the query in step 110), the method 100 continues to step 114 and receives client input data representative of third party evaluator selection or identification. The system then obtains a vehicle valuation from the one or more evaluators selected or otherwise identified by the client (step 116).

As a first example of how the vehicle valuation may be obtained by the host system, a data field may be generated which includes the comprehensive original vehicle data (and in some embodiments any supplemental data) and then transmitted to the selected one or more third party evaluators. The vehicle identifier may in some cases be provided as well, but typically the vehicle data alone will be sufficient. The evaluator may then populate the data field with any additional requested or required information, including vehicle valuation data. The vehicle valuation data may include a vehicle valuation and any other data which may be useful or available with respect to the particular evaluator, or as requested by the system. The vehicle valuation data may include for example a first vehicle valuation based on the original data and a second vehicle valuation which is based on the original data and any available supplemental data, such that either may be displayed for the client based on client selection.

In a second example, the data field is generated by the system as described above. However, rather than transmitting the data field itself to the evaluator, the system may generate and transmit a valuation request to the selected third parties via the dedicated interface (e.g., web page, email, direct download, etc.), with the request comprising at least a portion of the comprehensive original vehicle data as determined to be relevant for valuation by the particular evaluators. The system may then receive the requested vehicle valuation data from the third party in any of a number of available formats, and subsequently populates the data field with a vehicle valuation based on the received vehicle valuation data, or otherwise stores the vehicle valuation data or a valuation derived therefrom in the database.

In a third example, the data field is generated as described above and then transmitted to the one or more selected/identified third party evaluators. Rather than return the data field to the host, the evaluator may simply provide the requested vehicle valuation data via for example an email or the like. The host receives the vehicle valuation data and then populates the data field with a vehicle valuation based on the received vehicle valuation data, or otherwise stores the valuation in the database in association with the original vehicle data.

The method 100 as represented in FIG. 2 may further in step 118 include determining whether or not supplemental data is available with respect to the identified vehicle (or whether the supplemental data feature is available in a given embodiment). If supplemental data is not available (for either reason), the method may proceed to step 124, and the system generates a client response interface which includes or otherwise displays some or all of the vehicle information results. Typically, the interface will not include all of the comprehensive vehicle information (which may be quite lengthy), but rather one or more subsets of the data in accordance with a predetermined template that is populated with the respective data. One or more templates may be provided for user selection in various embodiments, or for example a list of optional data sets may be provided to the user and a template created from a subsequent user selection. The interface may be a web page or part of a mobile device application, in which the results may be pushed out by the host system via the communications network and displayed, or for example an email having text results or an embedded electronic file with the results, or various alternative and equivalent interfaces as may be known to those of skill in the art.

If supplemental data is available (i.e., “yes” in response to the query of step 118), the method proceeds to step 120 and indicates to the client the presence of supplemental data associated with the identified vehicle. The system may further indicate the service provider that was the source of the supplemental data, and where supplemental data has been provided from more than one service provider, each provider may for example be listed. If the system is programmed or configured to determine a reliability score or otherwise collect feedback regarding the various service providers, such information may be provided as well for review by the client.

In step 122, the client may then provide input to the system representative of selection or rejection of one or more of the service providers and associated supplemental data for inclusion in the final report or displayed results, wherein the method 100 proceeds to step 124 as described above.

The system may be configured to receive and compare sets of information from a plurality of sources. The system may be further configured to compare at least a portion of the sets of information to one another and/or to known correct information. A result of the comparison may be conveyed to a requesting client. As part of the comparison, a set of known information known by each of the plurality of sources may be matched against each source. The result of the comparison may include an indication of the results of the matching process, including one or more errors associated with a specific of the plurality of sources relating to known information.

A vehicle valuation process may include comparing known information to at least one of a set of common information between third parties or a set of distinguishing information between third parties. The process may include obtaining a vehicle valuation for the identified set of vehicle data from a plurality of third party evaluators via the communications network, identifying a common set of information relating to the identified set of vehicle data from each of the plurality of third party evaluators, identifying a distinguishing set of information relating to the identified set of vehicle data from each of the plurality of third party evaluators, and generating the client response interface displaying the vehicle valuation in association with the identified set of comprehensive original vehicle data, the identified common set of information, and the identified distinguishing set of information.

For example, a first of three sources may erroneously identify a particular model, thereby impacting that source's estimated insurance or valuation estimate. A reader of the results would clearly recognize this difference, and at least one of a user or the system may compensate accordingly (e.g., by discrediting a source having incorrect information or by excluding that source from the results presented to a client). Additionally or alternatively, the system may recognize a source having superior vehicle information as compared to another source, and may highlight a more accurate estimate in the report.

The previous detailed description has been provided for the purposes of illustration and description. Thus, although there have been described particular embodiments of the present disclosure of a new and useful “Web-Based System and Method for Providing Comprehensive Vehicle Build Information,” it is not intended that such references be construed as limitations upon the scope of this disclosure except as set forth in the following claims. 

What is claimed is:
 1. A computer-implemented method of generating comprehensive vehicle data, the computer-implemented method comprising: electronically accessing, at a hosted server, a set of comprehensive original vehicle data for one or more of a plurality of vehicles from one or more respective vehicle manufacturers via a vehicle source interface electronically linked to a communications network comprising one or more electronic networks, wherein each of the sets of comprehensive original vehicle data is associated with a respective unique vehicle identifier and includes: standard vehicle data associated with the unique vehicle identifier, the standard vehicle data being coded by a respective vehicle manufacturer of the one or more respective vehicle manufacturers, and factory vehicle build data associated with the unique vehicle identifier, the factory vehicle build data comprising original raw vehicle build data which is not included within the standard vehicle data and is not coded by the respective vehicle manufacturer into the unique vehicle identifier; wherein the set of comprehensive original vehicle data includes purchaser data associated with the plurality of vehicles and the respective purchaser data is required to be provided to an original purchaser of the respective vehicle; storing the set of comprehensive original vehicle data for each of the one or more plurality of vehicles in a database; receiving a vehicle information request from a client via a client request interface, the request including a received vehicle identifier; identifying a requested set of comprehensive original vehicle data stored in the database based on the received vehicle identifier from the client request; automatically generating a vehicle trim level attribute value for the respective vehicle identified by the received vehicle identifier based on applying one or more stored trim level assessments related to the make or model to original raw vehicle build data for the corresponding vehicle, wherein the one or more trim level assessments independently analyze details for the respective vehicle generated at a time of build for the respective vehicle without subsequent verification; comparing the vehicle trim level attribute value to original vehicle loan data for the respective vehicle identified by the received vehicle identifier; identifying inconsistencies between the vehicle trim level attribute value and the original vehicle loan data, wherein the inconsistencies include one or more misrepresentations or errors; and generating instructions for a client response interface to display vehicle data from the identified set of comprehensive original vehicle data and inconsistencies between the vehicle trim level attribute value and the original vehicle loan data.
 2. The computer-implemented method of claim 1, further comprising: converting the set of comprehensive original vehicle data into a universal format, wherein the database is effective to receive the original raw vehicle build data from one or more of a plurality of vehicle manufacturer systems associated with a plurality of original data formats.
 3. The computer-implemented method of claim 1, further comprising: determining a vehicle valuation for the requested set of comprehensive original vehicle data based on one or more predetermined valuation criteria and the vehicle trim level attribute value, and generating instructions for the client response interface to display the vehicle valuation in association with the requested set of comprehensive original vehicle data.
 4. The computer-implemented method of claim 1, wherein the comparing is based on applying one or more stored loan comparison assessments, wherein the one or more loan comparison assessments independently analyzes and compares details from the vehicle trim level attribute value to details from the original vehicle loan data.
 5. The computer-implemented method of claim 1, wherein the inconsistencies are associated with: an exposure assessment, a risk assessment, a liability assessment, or a lost revenue assessment.
 6. The computer-implemented method of claim 1, wherein the original vehicle loan data comprises one or more of: equipment, trim details, color, transmission details, drive train, factory packages, or factory options for the respective vehicle.
 7. The computer-implemented method of claim 1, wherein the purchaser data comprises data determined to be relevant for valuation.
 8. A system comprising: an original vehicle data system configured to electronically access a set of comprehensive original vehicle data for one or more of a plurality of vehicles from one or more respective vehicle manufacturers via a vehicle source interface electronically linked to a communications network comprising one or more electronic networks, wherein each of the sets of comprehensive original vehicle data is associated with a respective unique vehicle identifier and includes: standard vehicle data associated with the unique vehicle identifier, the standard vehicle data being coded by a respective vehicle manufacturer of the one or more respective vehicle manufacturers, and factory vehicle build data associated with the unique vehicle identifier, the factory vehicle build data comprising original raw vehicle build data which is not included within the standard vehicle data and is not coded by the respective vehicle manufacturer into the unique vehicle identifier; wherein the set of comprehensive original vehicle data includes purchaser data associated with the plurality of vehicles and the respective purchaser data is required to be provided to an original purchaser of the respective vehicle; an application programming interface configured to receive a vehicle information request from a client via a client request interface, the request including a received vehicle identifier; a vehicle trim component configured to: identify a requested set of comprehensive original vehicle data based on the received vehicle identifier from the client request; and automatically generate a vehicle trim level attribute value for the respective vehicle identified by the received vehicle identifier based on applying one or more stored trim level assessments related to the make or model to original raw vehicle build data for the corresponding vehicle, wherein the one or more trim level assessments independently analyze details for the respective vehicle generated at a time of build for the respective vehicle without subsequent verification; compare the vehicle trim level attribute value to original vehicle loan data for the respective vehicle identified by the received vehicle identifier; identify inconsistencies between the vehicle trim level attribute value and the original vehicle loan data, wherein the inconsistencies include one or more misrepresentations or errors; and a response system configured to generate instructions for a client response interface to display vehicle data from the identified set of comprehensive original vehicle data and inconsistencies between the vehicle trim level attribute value and the original vehicle loan data.
 9. The system of claim 8, wherein the standard vehicle data comprises one or more of: a country of origin, manufacturer, year of manufacture, manufacturing assembly plant, make, or model for the respective vehicle and the factory vehicle data comprises one or more of: equipment, trim details, color, transmission details, drive train, factory packages, or factory options for the respective vehicle.
 10. The system of claim 8, wherein the vehicle trim component is further configured to convert the original raw vehicle build data into a universal format wherein the database is effective to receive the original raw vehicle build data from one or more of a plurality of vehicle manufacturer systems associated with a plurality of original data formats.
 11. The system of claim 8, wherein the comparing is based on applying one or more stored loan comparison assessments, wherein the one or more loan comparison assessments independently analyzes and compares details from the vehicle trim level attribute value to details from the original vehicle loan data.
 12. The system of claim 8, wherein the inconsistencies are associated with: an exposure assessment, a risk assessment, a liability assessment, or a lost revenue assessment.
 13. The system of claim 8, wherein the original vehicle loan data comprises one or more of: equipment, trim details, color, transmission details, drive train, factory packages, or factory options for the respective vehicle.
 14. The system of claim 8, wherein the purchaser data comprises data determined to be relevant for valuation.
 15. A non-transitory computer storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to at least: electronically access a set of comprehensive original vehicle data for one or more of a plurality of vehicles from one or more respective vehicle manufacturers via a vehicle source interface electronically linked to a communications network comprising one or more electronic networks, wherein each of the sets of comprehensive original vehicle data is associated with a respective unique vehicle identifier and includes: standard vehicle data associated with the unique vehicle identifier, the standard vehicle data being coded by a respective vehicle manufacturer of the one or more respective vehicle manufacturers, and factory vehicle build data associated with the unique vehicle identifier, the factory vehicle build data comprising original raw vehicle build data which is not included within the standard vehicle data and is not coded by the respective vehicle manufacturer into the unique vehicle identifier; wherein the set of comprehensive original vehicle data includes purchaser data associated with the plurality of vehicles and the respective purchaser data is required to be provided to an original purchaser of the respective vehicle; store the set of comprehensive original vehicle data for each of the one or more plurality of vehicles in a database; receive a vehicle information request from a client via a client request interface, the request including a received vehicle identifier; identify a requested set of comprehensive original vehicle data stored in the database based on the received vehicle identifier from the client request; automatically generate a vehicle trim level attribute value for the respective vehicle identified by the received vehicle identifier based on applying one or more stored trim level assessments related to the make or model to original raw vehicle build data for the corresponding vehicle, wherein the one or more trim level assessments independently analyze details for the respective vehicle generated at a time of build for the respective vehicle without subsequent verification; compare the vehicle trim level attribute value to original vehicle loan data for the respective vehicle identified by the received vehicle identifier; identify inconsistencies between the vehicle trim level attribute value and the original vehicle loan data, wherein the inconsistencies include one or more misrepresentations or errors; and generate instructions for a client response interface to display vehicle data from the identified set of comprehensive original vehicle data and inconsistencies between the vehicle trim level attribute value and the original vehicle loan data.
 16. The non-transitory computer storage medium of claim 15, further storing computer-executable instructions that, when executed by a processor, cause the processor to: convert the set of comprehensive original vehicle data into a universal format, wherein the database is effective to receive the original raw vehicle build data from one or more of a plurality of vehicle manufacturer systems associated with a plurality of original data formats.
 17. The non-transitory computer storage medium of claim 15, further storing computer-executable instructions that, when executed by a processor, cause the processor to: determine a vehicle valuation for the requested set of comprehensive original vehicle data based on one or more predetermined valuation criteria and the vehicle trim level attribute value, and generate instructions for the client response interface to display the vehicle valuation in association with the requested set of comprehensive original vehicle data.
 18. The non-transitory computer storage medium of claim 15, wherein the comparing is based on applying one or more stored loan comparison assessments, wherein the one or more loan comparison assessments independently analyzes and compares details from the vehicle trim level attribute value to details from the original vehicle loan data.
 19. The non-transitory computer storage medium of claim 15, wherein the inconsistencies are associated with: an exposure assessment, a risk assessment, a liability assessment, or a lost revenue assessment.
 20. The non-transitory computer storage medium of claim 15, wherein the original vehicle loan data comprises one or more of: equipment, trim details, color, transmission details, drive train, factory packages, or factory options for the respective vehicle.
 21. The non-transitory computer storage medium of claim 15, wherein the purchaser data comprises data determined to be relevant for valuation. 